Conversation-Aware Proactive Notifications for a Voice Interface Device

ABSTRACT

A method for proactive notifications in a voice interface device includes: receiving a first user voice request for an action with an future performance time; assigning the first user voice request to a voice assistant service for performance; subsequent to the receiving, receiving a second user voice request and in response to the second user voice request initiating a conversation with the user; and during the conversation: receiving a notification from the voice assistant service of performance of the action; triggering a first audible announcement to the user to indicate a transition from the conversation and interrupting the conversation; triggering a second audible announcement to the user to indicate performance of the action; and triggering a third audible announcement to the user to indicate a transition back to the conversation and rejoining the conversation.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/841,284, entitled “Conversation-Aware Proactive Notifications for a Voice Interface Device,” filed Dec. 13, 2017, which claims the benefit of U.S. Provisional Patent Application No. 62/441,116 entitled “Conversation-Aware Proactive Notifications for a Voice Interface Device,” filed Dec. 30, 2016, each of which is incorporated herein in its entirety.

This application is related to the following applications, which are incorporated by reference herein in their entirety:

U.S. patent application Ser. No. 15/801,307, entitled “Focus Session at a Voice Interface Device,” filed Nov. 1, 2017, which claims the benefit of U.S. Provisional Patent Application No. 62/417,281, entitled “Focus Session at a Voice Interface Device,” filed Nov. 3, 2016; U.S. patent application Ser. No. 15/592,137, entitled “Implementations for Voice Assistant on Devices,” filed May 10, 2017, which claims the benefit of U.S. Provisional Patent Application No. 62/334,434, entitled “Implementations for Voice Assistant on Devices,” filed May 10, 2016; and U.S. patent application Ser. No. 15/592,120, entitled “LED Design Language for Visual Affordance of Voice User Interfaces,” filed May 10, 2017, which claims the benefit of U.S. Provisional Patent Application No. 62/336,566, entitled “LED Design Language for Visual Affordance of Voice User Interfaces,” filed May 13, 2016.

TECHNICAL FIELD

The disclosed implementations relate generally to voice interfaces and related devices, including but not limited methods and systems for providing low-latency proactive voice notifications that are robust to long-term voice interface conversations.

BACKGROUND

Electronic devices with voice interfaces have been widely used to collect voice inputs from users and perform different voice-activated functions according to the voice inputs. These voice-activated functions may include directing or commanding a target device to perform an operation. For example, the user may utter a voice input to a voice interface device to direct a target device to turn on or off, or to control media playback at the target device.

Typically, if a user wishes to make a voice input that directs a target device to perform an operation, the user would specify the target device in the voice input. However, having to explicitly specify the target device for all such voice inputs is tedious and burdensome to the user. It is desirable for a voice interface device to have a target device for a voice input even when the voice input does not specify a target or specifies an ambiguous target.

Further, it is useful for a voice interface device to be able to inform the user of important updates. These “proactive notifications” can be things like a taxi car arriving, a food delivery arriving, a home security alert, or even that a sports team won or lost a game. However, the timeliness of the delivery of these proactive notifications can be impacted by other interactions the user has with the device. A user might be in the middle of a long interaction (e.g., a conversation, playing a game, or making a reservation) with the device, and providing the notification while the long interaction with the device is ongoing may break the flow of the interaction, which may be disruptive to the user and may even make the use start over. On the other hand, if the notification delayed until the interaction is over, the notification may be untimely.

SUMMARY

Accordingly, there is a need for an electronic device with a voice assistant system and/or a voice assistant server system that incorporates methods and systems for determining or assigning a target device for a voice input when a specification of a target device in the voice input is absent or ambiguous. In various implementations described in this application, an operating environment includes a voice-activated electronic device that provides an interface to a voice assistant service, and multiple devices (e.g., cast device, smart home device) that may be controlled by voice input via the voice assistant service. The voice-activated electronic device is configured to record a voice input from which the voice assistance service (e.g., a voice assistance server system) determines a user voice request (e.g., a media playback request, a power state change request). The voice assistance server system then directs the user voice request to a target device as indicated by the voice input. The voice-activated electronic device is configured to record a subsequent voice input, in which an indication of a target device is absent or ambiguous. The electronic device or the voice assistance server system assigns a target device for this voice input, determines a user voice request included in this voice input, and directs the user voice request to the assigned target device.

In accordance with some implementations, a method is performed at a first electronic device with one or more microphones, a speaker, one or more processors, and memory storing one or more programs for execution by the one or more processors. The first electronic device is a member of a local group of connected electronic devices communicatively coupled to a common network service. The method includes: receiving a first voice command including a request for a first operation; determining a first target device for the first operation from among the local group of connected electronic devices; establishing a focus session with respect to the first target device; causing the first operation to be performed by the first target device via operation of the common network service; receiving a second voice command including a request for a second operation; determining that the second voice command does not include an explicit designation of a second target device; determining that the second operation can be performed by the first target device; determining whether the second voice command satisfies one or more focus session maintenance criteria; and in accordance with a determination that the second voice command satisfies the focus session maintenance criteria, causing the second operation to be performed by the first target device via operation of the common network service.

In accordance with some implementations, an electronic device includes one or more microphones, a speaker, one or more processors, and memory storing one or more programs to be executed by the one or more processors. The one or more programs include instructions for performing the method described above.

In accordance with some implementations, a non-transitory computer readable storage medium stores one or more programs. The one or more programs include instructions, which, when executed by an electronic device with one or more microphones, a speaker, and one or more processors, cause the electronic device to perform operations of the method described above.

Furthermore, there is a need for an electronic device with a voice assistant system and/or a voice assistant server system that incorporates methods and systems for providing proactive notifications in a manner that is aware of ongoing interactions between the user and the device. In various implementations described in this application, an operating environment includes a voice-activated electronic device that provides an interface to a voice assistant service. The voice-activated electronic device is configured to provide a voice interface that is configured to receive and record voice inputs, in response to which the voice assistance service (e.g., a voice assistance server system) provides voice outputs, performs operations, and so on; in this manner the user and the voice assistance service can interact through voice (e.g., as if in a conversation). When the voice assistance service is trying to provide a notification to the user, the device and/or voice assistance service determines if there is an ongoing interaction and if the interaction may be interrupted gracefully for the notification. If a graceful interruption is possible, outputs indicating a transition in and out of the notification are made, with the notification made in between the transition outputs. Otherwise, the notification may be made with an abrupt transition.

In accordance with some implementations, a method for proactive notifications in a voice interface device includes: receiving a first user voice request for an action with an future performance time; assigning the first user voice request to a voice assistant service for performance; subsequent to the receiving, receiving a second user voice request and in response to the second user voice request initiating a conversation with the user; and during the conversation: receiving a notification from the voice assistant service of performance of the action; triggering a first audible announcement to the user to indicate a transition from the conversation and interrupting the conversation; triggering a second audible announcement to the user to indicate performance of the action; and triggering a third audible announcement to the user to indicate a transition back to the conversation and rejoining the conversation.

In accordance with some implementations, an electronic device includes a speaker, one or more processors, and memory storing one or more programs configured for execution by the one or more processors. The one or more programs include instructions for performing the method described above. In accordance with some implementations, the one or more programs include instructions for performing the method described above in cooperation with one or more servers with which the electronic device is interconnected.

In accordance with some implementations, a server includes one or more processors, and memory storing one or more programs configured for execution by the one or more processors. The one or more programs include instructions for performing the method described above.

In accordance with some implementations, a non-transitory computer readable storage medium stores one or more programs. The one or more programs include instructions, which, when executed by an electronic device with a speaker and one or more processors, cause the electronic device to perform the method described above. In some accordance with some implementations, the one or more programs include instructions, which, when executed by the electronic device, cause the electronic device to perform the method described above in cooperation with one or more servers with which the electronic device is interconnected.

In accordance with some implementations, a non-transitory computer readable storage medium stores one or more programs. The one or more programs include instructions, which, when executed by a server with one or more processors, cause the electronic device to perform the method described above.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described implementations, reference should be made to the Description of Implementations below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.

FIG. 1 illustrates an example operating environment in accordance with some implementations.

FIG. 2 illustrates an example voice-activated electronic device in accordance with some implementations.

FIGS. 3A-3B illustrates an example voice assistance server system in accordance with some implementations.

FIG. 3C illustrates an example functional block diagram of a voice assistance system that provides proactive notifications in accordance with some implementations;

FIG. 3D illustrates stored data associated with the voice assistance system of FIG. 3C in accordance with some implementations;

FIGS. 4A-4D illustrates an example of a focus session in accordance with some implementations.

FIG. 5 illustrates a flow diagram of an example process of establishing a focus session and responding to voice inputs in accordance with a focus session, in accordance with some implementations.

FIG. 6 illustrates a flow diagram of an example process for proactive notifications in a voice interface device, in accordance with some implementations.

Like reference numerals refer to corresponding parts throughout the several views of the drawings.

DESCRIPTION OF IMPLEMENTATIONS

While the digital revolution has provided many benefits ranging from openly sharing information to a sense of global community, emerging new technology often induces confusion, skepticism and fear among consumers, preventing consumers from benefitting from the technology. Electronic devices are conveniently used as voice interfaces to receive voice inputs from users and initiate voice-activated functions, and thereby offer eyes-free and hands-free solutions to approach both existing and emerging technology. Specifically, the voice inputs received at the electronic device can carry instructions and information even if a user's line of sight is obscured and his hands are full. To enable a hands-free and eyes-free experience, the voice-activated electronic device listens to the ambient (i.e., constantly processes audio signals collected from the ambient) constantly or only when triggered. On the other hand, user identities are linked with a user's voice and a language used by the user. To protect the user identities, these voice-activated electronic devices are normally used in non-public places that are protected, controlled and intimate spaces (e.g., home and car).

In accordance with some implementations, a voice-activated electronic device determines or assigns a target device to a request made in a voice command when an indication of a target device in the voice command is absent or ambiguous. The voice-activated electronic device establishes focus sessions with respect to a target device explicitly specified or indicated in a voice command. When the voice-activated electronic device receives a subsequent voice command in which a specification or indication of a target device is absent or ambiguous, the electronic device assigns the target device of the focus session to the voice command if the voice command satisfies one or more criteria.

In some implementations, when the user talks to a voice interface device to control another device, the voice interface device stores which device was being targeted by the user (e.g., in a focus session). For a period after that, the default target device for control is the stored device. For example, if the user first utters a voice command, “turn on the kitchen light,” and then utters, “turn off the light,” the target device for the second voice command defaults to “kitchen light” if the second command is received shortly after the first command. As another example, if the first command is “play music on living room speakers,” and the subsequent command is “stop music,” the target device for the second voice command defaults to “living room speakers” if the second command is received shortly after the first command.

Additionally, in some implementations, the user may be asked to confirm or verify that the last used target device is the intended target device, if there is a longer time gap between voice inputs. For example, if the first voice command is, “play music on living room speakers,” and the subsequent command, receiving after a longer time gap from the first voice command, is “stop music,” the voice interface device may ask the user, “do you want to stop the music on the living room speakers?” to confirm that the target device is “living room speakers.”

In this way, the user may be spared the burden of having to specify the full context of his request in each and every voice input (e.g., spared from having to include a specification of a target device in each and every voice input requesting an operation to be performed).

In accordance with some implementations, a voice-activated electronic device provides low-latency proactive notifications in a manner that is robust to long-term interactions between the user and the device. In some implementations, there is a voice-activated electronic device, a conversation manager (e.g., a conversation manager module), a notification manager (e.g., notification manager module) that can determine if or what notifications need to be delivered, and an agent (e.g., an agent module and/or system) the conversation manager talks to. The agent may be, for example, a vacation reservation system.

In some implementations, the conversation manager, which can determine the state of the interaction with the user, also can determine if there is a proactive notification or update that needs to be provided to the user.

For example, in the middle of an ongoing interaction (e.g., a “conversation” between the user and the agent via the device), assume a notification comes in. The conversation manager asks the agent if the agent can support an interruption in the interaction with the user. If the agent cannot support the interruption, the conversation manager may preempt the user's interaction with the agent and immediately provide the user with the audible notification (e.g., direct the device to output the notification as a voice output). The voice output of the notification may say, for example, “sorry, but I need to interrupt, <notification>”.

In some implementations, if the agent can support an interruption, the agent may be given an opportunity to supply a transition out and transition in dialog to transition out of the interaction so that the notification can be given, and then transition back into the interaction. In some implementations, when there is no ongoing conversation between the user and an agent, the conversation manager can simply cause the device to issue the notification at an appropriate time (e.g., in view of user settings and the nature of the notification) without needing to interact with an agent as described above.

In this manner, important notifications may be delivered immediately or otherwise in a timely manner, without completely stopping interactions, or having very abrupt or polite transitions between agents with which the user are interacting.

Voice Assistant Operating Environment

FIG. 1 is an example operating environment in accordance with some implementations. Operating environment 100 includes one or more voice-activated electronic devices 104 (e.g., voice-activated electronic devices 104-1 thru 104-N, hereinafter “voice-activated device(s)”). The one or more voice-activated devices 104 may be located in one or more locations (e.g., all in a room or space of a structure, spread out throughout multiple spaces within a structure or throughout multiple structures (e.g., one in a house and one in the user's car)).

The environment 100 also includes one or more controllable electronic devices 106 (e.g., electronic device 106-1 thru 106-N, hereinafter “controllable device(s)”). Examples of controllable devices 106 include media devices (smart televisions, speaker systems, wireless speakers, set-top boxes, media streaming devices, cast devices), and smart home devices (e.g., smart camera, smart thermostat, smart light, smart hazard detector, smart door lock).

The voice-activated devices 104 and the controllable devices 106 are communicatively coupled, through communication networks 110, to a voice assistant service 140 (e.g., to a voice assistance server system 112 of the voice assistant service 140). In some implementations, one or more of the voice-activated devices 104 and the controllable devices 106 are communicatively coupled to a local network 108, which is communicatively coupled to the communication networks 110; the voice-activated device(s) 104 and/or the controllable device(s) 106 are communicatively coupled to communication network(s) 110 (and, through the communication networks 110, to the voice assistance server system 112) via the local network 108. In some implementations, the local network 108 is a local area network implemented at a network interface (e.g., a router). The voice-activated devices 104 and the controllable devices 106 that are communicatively coupled to the local network 108 may also communicate with each other through the local network 108.

Optionally, one or more of the voice-activated devices 104 are communicatively coupled to the communication networks 110 and are not on the local network 108. For example, these voice-activated devices are not on the Wi-Fi network corresponding to the local network 108 but are connected to the communication networks 110 through a cellular connection. In some implementations, communication between voice-activated devices 104 that are on the local network 108 and voice-activated devices 104 that are not on the local network 108 are done through the voice assistance server system 112. The voice-activated devices 104 (whether on the local network 108 or on the network 110) are registered in a device registry 118 of the voice assistant service 140 and thus known to the voice assistance server system 112. Similarly, the voice-activated devices 104 that are not on the local network 108 may communicate with controllable devices 106 through the voice assistant server system 112. The controllable devices 106 (whether on the local network 108 or on the network 110) are also registered in the device registry 118. In some implementations, communications between the voice-activated devices 104 and the controllable devices 106 go through the voice assistance server system 112.

In some implementations, the environment 100 also includes one or more content hosts 114. A content host 114 may be a remote content source from which content is streamed or otherwise obtained in accordance with a request included in a user voice input or command. A content host 114 may be an information source from which the voice assistance server system 112 retrieves information in accordance with a user voice request.

In some implementations, controllable devices 106 are capable of receiving commands or requests to perform specified operations or to transition to specified states (e.g., from a voice-activated device 104 and/or the voice assistance server system 112) and to perform the operations or transition states in accordance with the received commands or requests.

In some implementations, one or more of the controllable devices 106 are media devices that are disposed in the operating environment 100 to provide to one or more users media content, news and/or other information. In some implementations, the content provided by the media devices is stored at a local content source, streamed from a remote content source (e.g., content host(s) 114), or generated locally (e.g., through a local text to voice processor that reads a customized news briefing, emails, texts, a local weather report, etc. to one or more occupants of the operating environment 100). In some implementations, the media devices include media output devices that directly output the media content to an audience (e.g., one or more users), and cast devices that are networked to stream media content to the media output devices. Examples of the media output devices include, but are not limited to television (TV) display devices and music players. Examples of the cast devices include, but are not limited to, set-top boxes (STBs), DVD players, TV boxes, and media streaming devices, such as Google's Chromecast™ media streaming device.

In some implementations, a controllable device 106 is also a voice-activated device 104. In some implementations, a voice-activated device 104 is also a controllable device 106. For example, a controllable device 106 may include a voice interface to the voice assistance service 140 (e.g., a media device that can also receive, process, and respond to user voice inputs). As another example, a voice-activated device 104 may also perform particular operations and transition to particular states in accordance with requests or commands in voice inputs (e.g., a voice interface device that can also play streaming music).

In some implementations, the voice-activated devices 104 and the controllable deices 106 are associated with a user having a respective account, or with multiple users (e.g., a group of related users, such as users in a family or in an organization; more generally, a primary user and one or more authorized additional users) having respective user accounts, in a user domain. A user may make voice inputs or voice commands to the voice-activated device 104. The voice-activated device 104 receives these voice inputs from the user (e.g., user 102), and the voice-activated device 104 and/or the voice assistance server system 112 proceeds to determine a request in the voice input and generate a response to the request.

In some implementations, the request included in a voice input is a command or request to a controllable device 106 to perform an operation (e.g., play media, pause media, fast forward or rewind media, change volume, change screen brightness, change light brightness) or transition to another state (e.g., change the mode of operation, turn on or off, go into sleep mode or wake from sleep mode).

In some implementations, a voice-activated electronic device 104 responds to voice inputs by: generating and providing a spoken response to a voice command (e.g., speaking the current time in response to the question, “what time is it?”); streaming media content requested by a user (e.g., “play a Beach Boys song”); reading a news story or a daily news briefing prepared for the user; playing a media item stored on the personal assistant device or on the local network; changing a state or operating one or more other connected devices within the operating environment 100 (e.g., turning lights, appliances or media devices on/off, locking/unlocking a lock, opening windows, etc.); or issuing a corresponding request to a server via a network 110.

In some implementations, the one or more voice-activated devices 104 are disposed in the operating environment 100 to collect audio inputs for initiating various functions (e.g., media play functions of the media devices). In some implementations, these voice-activated devices 104 (e.g., devices 104-1 thru 104-N) are disposed in proximity to a controllable device 104 (e.g., a media device), for example, in the same room with the cast devices and the media output devices. Alternatively, in some implementations, a voice-activated device 104 is disposed in a structure having one or more smart home devices but not any media device. Alternatively, in some implementations, a voice-activated device 104 is disposed in a structure having one or more smart home devices and one or more media devices. Alternatively, in some implementations, a voice-activated device 104 is disposed in a location having no networked electronic device. Further, in some implementations, a room or space in the structure may have multiple voice-activated devices 104.

In some implementations, the voice-activated device 104 includes at least one or more microphones, a speaker, a processor and memory storing at least one program for execution by the processor. The speaker is configured to allow the voice-activated device 104 to deliver voice messages and other audio (e.g., audible tones) to a location where the voice-activated device 104 is located in the operating environment 100, thereby broadcasting music, reporting a state of audio input processing, having a conversation with or giving instructions to a user of the voice-activated device 104. As an alternative to the voice messages, visual signals could also be used to provide feedback to the user of the voice-activated device 104 concerning the state of audio input processing. When the voice-activated device 104 is a mobile device (e.g., a mobile phone or a tablet computer), its display screen is configured to display a notification concerning the state of audio input processing.

In some implementations, the voice-activated device 104 is a voice interface device that is network-connected to provide voice recognition functions with the aid of a voice assistance server system 112. For example, the voice-activated device 104 includes a smart speaker that provides music to a user and allows eyes-free and hands-free access to a voice assistant service (e.g., Google Assistant). Optionally, the voice-activated device 104 is one of a desktop or laptop computer, a tablet, a mobile phone that includes a microphone, a cast device that includes a microphone and optionally a speaker, an audio system (e.g., a stereo system, a speaker system, a portable speaker) that includes a microphone and a speaker, a television that includes a microphone and a speaker, and a user interface system in an automobile that includes a microphone and a speaker and optionally a display. Optionally, the voice-activated device 104 is a simple and low cost voice interface device. Generally, the voice-activated device 104 may be any device that is capable of network connection and that includes a microphone, a speaker, and programs, modules, and data for interacting with voice assistant service. Given simplicity and low cost of the voice-activated device 104, the voice-activated device 104 includes an array of light emitting diodes (LEDs) rather than a full display screen, and displays a visual pattern on the LEDs to indicate the state of audio input processing. In some implementations, the LEDs are full color LEDs, and the colors of the LEDs may be employed as a part of the visual pattern to be displayed on the LEDs. Multiple examples of using LEDs to display visual patterns in order to convey information or device status are described in U.S. Provisional Patent Application No. 62/336,566, entitled “LED Design Language for Visual Affordance of Voice User Interfaces,” filed May 13, 2016, which is incorporated by reference in its entirety. In some implementations, visual patterns indicating the state of voice processing operations are displayed using characteristic images shown on conventional displays associated with voice-activated devices that are performing the voice processing operations.

In some implementations, LEDs or other visual displays are used to convey a collective voice processing state of multiple participating electronic devices. For example, in an operating environment where there are multiple voice processing or voice interface devices (e.g., multiple electronic devices 104 as shown in FIG. 4A of the '566 application; multiple voice-activated devices 104 of FIG. 1), groups of color LEDs (e.g., LEDs 404 as shown in FIG. 4A of the '566 application) associated with respective electronic devices can be used to convey which of the electronic devices is listening to a user, and which of the listening devices is the leader (where the “leader” device generally takes the lead in responding to a spoken request issued by the user).

More generally, the '566 application describes (e.g., see paras. [0087]-[0100]) a “LED Design Language” for indicating visually using a collection of LEDs a variety of voice processing states of an electronic device, such as a hot word detection state, a listening state, a thinking mode, working mode, a Responding mode or speaking mode, and a proactive notification mode. In some implementations, unique states of voice processing operations described herein are represented using a group of LEDs in accordance with one or more aspects of the “LED Design Language” of the '566 application. These visual indicators can also be combined with one or more audible indicators generated by electronic devices that are performing voice processing operations. The resulting audio and/or visual indicators will enable users in a voice-interactive environment to understand the state of various voice processing electronic devices in the environment and to effectively interact with those devices in a natural, intuitive manner.

In some implementations, when voice inputs to the voice-activated device 104 are used to control the media output devices via the cast devices, the voice-activated device 104 effectively enables a new level of control of cast-enabled media devices. In a specific example, the voice-activated device 104 includes a casual enjoyment speaker with far-field voice access and functions as a voice interface device for the voice assistant service. The voice-activated device 104 could be disposed in any area in the operating environment 100. When multiple voice-activated devices 104 are distributed in multiple rooms, they become cast audio receivers that are synchronized to provide voice inputs from these rooms.

Specifically, in some implementations, the voice-activated device 104 includes a Wi-Fi speaker with a microphone that is connected to a voice-activated voice assistant service (e.g., Google Assistant). A user can issue a media play request via the microphone of voice-activated device 104, and ask the voice assistant service to play media content on the voice-activated device 104 itself or on another connected media output device. For example, the user can issue a media play request by saying to the Wi-Fi speaker “OK Google, play cat videos on my Living room TV.” The voice assistant service then fulfils the media play request by playing the requested media content on the requested device using a default or designated media application.

In some implementations, a user can issue a voice request, via the microphone of the voice-activated device 104, concerning media content that has already been played or is being played on a display device (e.g., the user can ask for information about the media content, buy the media content through an online store, or compose and issue a social post about the media content).

In some implementations, a user may want to take a current media session with them as they move through the house and can request such a service from one or more of the voice-activated devices 104. This requires the voice assistant service 140 to transfer the current media session from a first cast device to a second cast device that is not directly connected to the first cast device or has no knowledge of the existence of the first cast device. Subsequent to the media content transfer, a second output device coupled to the second cast device continues to play the media content previously a first output device coupled to the first cast device from the exact point within a music track or a video clip where play of the media content was forgone on the first output device. In some implementations, the voice-activated device 104 that receives the request to transfer the media session can satisfy the request. In some implementations, the voice-activated device 104 that receives the request to transfer the media session relays the request to another device or system (e.g., voice assistance server system 112) for handling.

Further, in some implementations, a user may issue, via the microphone of voice-activated device 104, a request for information or for performance of an action or operation. The information requested may be personal (e.g., the user's emails, the user's calendar events, the user's flight information, etc.), non-personal (e.g., sports scores, news stories, etc.) or somewhere in between (e.g., scores for teams or sports preferred by the user, news stories from the user's preferred sources, etc.). The requested information or action/operation may involve access to personal information (e.g., purchasing a digital media item with payment information provided by the user, purchasing a physical good). The voice-activated device 104 responds to the request with voice message responses to the user, where the response may include, for example, requests for additional information to fulfill the request, confirmation that the request has been fulfilled, notice that the request cannot be fulfilled, and so forth.

In some implementations, in addition to the voice-activated devices 104 and the media devices amongst the controllable devices 106, the operating environment 100 may also include one or more smart home devices amongst the controllable devices 106. The integrated smart home devices include intelligent, multi-sensing, network-connected devices that integrate seamlessly with each other in a smart home network and/or with a central server or a cloud-computing system to provide a variety of useful smart home functions. In some implementations, a smart home device is disposed at the same location of the operating environment 100 as a cast device and/or an output device, and therefore, is located in proximity to or with a known distance with respect to the cast device and the output device.

The smart home devices in the operating environment 100 may include, but are not limited to, one or more intelligent, multi-sensing, network-connected thermostats, one or more intelligent, network-connected, multi-sensing hazard detectors, one or more intelligent, multi-sensing, network-connected entryway interface devices and (hereinafter referred to as “smart doorbells” and “smart door locks”), one or more intelligent, multi-sensing, network-connected alarm systems, one or more intelligent, multi-sensing, network-connected camera systems, one or more intelligent, multi-sensing, network-connected wall switches, one or more intelligent, multi-sensing, network-connected power sockets, and one or more intelligent, multi-sensing, network-connected lights. In some implementations, the smart home devices in the operating environment 100 of FIG. 1 includes a plurality of intelligent, multi-sensing, network-connected appliances (hereinafter referred to as “smart appliances”), such as refrigerators, stoves, ovens, televisions, washers, dryers, lights, stereos, intercom systems, garage-door openers, floor fans, ceiling fans, wall air conditioners, pool heaters, irrigation systems, security systems, space heaters, window AC units, motorized duct vents, and so forth. In some implementations, any one of these smart home device types can be outfitted with microphones and one or more voice processing capabilities as described herein so as to in whole or in part respond to voice requests from an occupant or user.

In some implementations, each of the controllable devices 104 and the voice-activated devices 104 is capable of data communications and information sharing with other controllable devices 106, voice-activated electronic devices 104, a central server or cloud-computing system, and/or other devices (e.g., a client device) that are network-connected. Data communications may be carried out using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety of custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

Through the communication networks (e.g., the Internet) 110, the controllable devices 106 and the voice-activated devices 104 may communicate with a server system (also called a central server system and/or a cloud-computing system herein). Optionally, the server system may be associated with a manufacturer, support entity, or service provider associated with the controllable devices and the media content displayed to the user. Accordingly, the server system includes the voice assistance server 112 that processes audio inputs collected by voice-activated devices 104, one or more content hosts 114 that provide the displayed media content, optionally a cloud cast service server creating a virtual user domain based on distributed device terminals, and the device registry 118 that keeps a record of the distributed device terminals in the virtual user environment. Examples of the distributed device terminals include, but are not limited to the controllable devices 106, the voice-activated devices 104, and the media output devices. In some implementations, these distributed device terminals are linked to a user account (e.g., a Google user account) in the virtual user domain. It should be appreciated that processing of audio inputs collected by voice-activated devices 104 can be performed locally at a voice-activated device 104, at a voice assistance server 112, at another smart home device (e.g., a hub device) or at some combination of all or subset of the above.

It will be appreciated that in some implementations the voice-activated device(s) 104 also function in an environment without smart home devices. For example, a voice-activated device 104 can, even in the absence of smart home devices, respond to user requests for information or performance of an action, and/or to initiate or control various media play functions. A voice-activated device 104 can also function in a wide range of environments, including, without limitation, a vehicle, a ship, a business, or a manufacturing environment.

In some implementations, a voice-activated device 104 is “awakened” (e.g., to activate an interface for the voice assistant service on the voice-activated device 104, to put the voice-activated device 104 into a state where the voice-activated device 104 is ready to receive voice requests to the voice assistant service) by a voice input that includes a hotword (also called a “wake word”). In some implementations, the voice-activated device 104 requires awakening if the voice-activated device 104 has been idle with respect to receipt of voice inputs for at least a predefined amount of time (e.g., 5 minutes); the predefined amount of time corresponds to an amount of idle time allowed before a voice interface session or conversation times out. The hotword may be a word or phrase, and may be a predefined default and/or may be customized by a user (e.g., a user may set a nickname for a particular voice-activated device 104 as the device's hotword). In some implementations, there may be multiple hotwords that can awaken a voice-activated device 104. A user may speak the hotword, wait for an acknowledgement response from the voice-activated device 104 (e.g., the voice-activated device 104 outputs a greeting), and them make a first voice request. Alternatively, the user may combine the hotword and the first voice request in one voice input (e.g., the voice input includes the hotword followed by the voice request).

In some implementations, a voice-activated device 104 interacts with a controllable device 106 (e.g., a media device, a smart home device), a client device or a server system of an operating environment 100 in accordance with some implementations. The voice-activated device 104 is configured to receive audio inputs from an environment in proximity to the voice-activated device 104. Optionally, the voice-activated device 104 stores the audio inputs and at leasft partially processes the audio inputs locally. Optionally, the voice-activated device 104 transmits the received audio inputs or the partially processed audio inputs to a voice assistance server system 112 via the communication networks 110 for further processing. The voice-activated device 104 or the voice assistance server system 112 determines if there is a request in the audio input and what the request is, determines and generates a response to the request, and transmits the request to one or more controllable device(s) 106. The controllable device(s) 106 receiving the response is configured to perform operations or change states in accordance with the response. For example, a media device is configured to obtain media content or Internet content from one or more content hosts 114 for display on an output device coupled to the media device, in accordance with a response to a request in the audio input.

In some implementations, the controllable device(s) 106 and the voice-activated device(s) 104 are linked to each other in a user domain, and more specifically, associated with each other via a user account in the user domain. Information on the controllable device 106 (whether on the local network 108 or on the network 110) and the voice-activated device 104 (whether on the local network 108 or on the network 110) are stored in the device registry 118 in association with the user account. In some implementations, there is a device registry for controllable devices 106 and a device registry for voice-activated devices 104. The controllable devices registry may reference devices in the voice-activated devices registry that are associated in the user domain, and vice versa.

In some implementations, one or more of the voice-activated devices 104 (and one or more cast devices) and one or more of the controllable devices 106 are commissioned to the voice assistant service 140 via a client device 103. In some implementations, the voice-activated device 104 does not include any display screen, and relies on the client device 103 to provide a user interface during a commissioning process, and similarly for a controllable device 106 as well. Specifically, the client device 103 is installed with an application that enables a user interface to facilitate commissioning of a new voice-activated device 104 and/or a controllable device 106 disposed in proximity to the client device. A user may send a request on the user interface of the client device 103 to initiate a commissioning process for the new electronic device 104/106 that needs to be commissioned. After receiving the commissioning request, the client device 103 establishes a short range communication link with the new electronic device 104/103 that needs to be commissioned. Optionally, the short range communication link is established based near field communication (NFC), Bluetooth, Bluetooth Low Energy (BLE) and the like. The client device 103 then conveys wireless configuration data associated with a wireless local area network (WLAN) (e.g., local network 108) to the new or electronic device 104/106. The wireless configuration data includes at least a WLAN security code (i.e., service set identifier (SSID) password), and optionally includes a SSID, an Internet protocol (IP) address, proxy configuration and gateway configuration. After receiving the wireless configuration data via the short range communication link, the new electronic device 104/106 decodes and recovers the wireless configuration data, and joins the WLAN based on the wireless configuration data.

In some implementations, additional user domain information is entered on the user interface displayed on the client device 103, and used to link the new electronic device 104/106 to an account in a user domain. Optionally, the additional user domain information is conveyed to the new electronic device 104/106 in conjunction with the wireless communication data via the short range communication link. Optionally, the additional user domain information is conveyed to the new electronic device 104/106 via the WLAN after the new device has joined the WLAN.

Once the electronic device 104/106 has been commissioned into the user domain, other devices and their associated activities may be controlled via multiple control paths. In accordance with one control path, an application installed on the client device 103 is used to control the other device and its associated activities (e.g., media play activities). Alternatively, in accordance with another control path, the electronic device 104/106 is used to enable eyes-free and hands-free control of the other device and its associated activities.

In some implementations, voice-activated devices 104 and controllable devices 106 may be assigned nicknames by a user (e.g., by the primary user with whom the devices are associated in the user domain). For example, a speaker device in the living room may be assigned a nickname “living room speaker.” In this way, the user may more easily refer to a device in a voice input by speaking the device's nickname. In some implementations, the device nicknames and mappings to corresponding devices are stored at a voice-activated device 104 (which would store the nicknames of just the devices associated with the same user as the voice-activated device) and/or the voice assistance server system 112 (which would store deice nicknames of devices associated with different users). For example, the voice assistance server system 112 stores many device nicknames and mappings across different devices and users, and voice-activated devices 104 associated with a particular user download nicknames and mappings for devices associated with the particular user for local storage.

In some implementations, a user may group one or more of the voice-activated devices 104 and/or controllable devices 106 into a group of devices created by the user. The group may be given a name, and the group of devices may be referred by the group name, similarly to referring to individual devices by nickname. Similar to device nicknames, device groups and group names may be stored at a voice-activated device 104 and/or the voice assistance server system 112.

A voice input from the user may explicitly specify a target controllable device 106 or a target group of devices for the request in the voice input. For example, a user may utter a voice input “play classical music on the living room speaker.” The target device in the voice input is “living room speaker”; the request in the voice input is a request to have the “living room speaker” play classical music. As another example, a user may utter a voice input “play classical music on the house speakers,” where “house speakers” is a name of a group of devices. The target device group in the voice input is “house speakers”; the request in the voice input is a request to have the devices in the group “house speakers” play classical music.

A voice input from the user may not have an explicit specification of a target device or device group; a reference to a target device or device group by name is absent in the voice input. For example, following on the example voice input “play classical music on the living room speaker” above, the user may utter a subsequent voice input “pause.” The voice input does not include a target device specification for the request for a pause operation. In some implementations, the target device specification in the voice input may be ambiguous. For example, the user may have uttered the device name incompletely. In some implementations, a target device or device group may be assigned to the voice input where an explicit target device specification is absent or the target device specification is ambiguous, as described below.

In some implementations, when a voice-activated device 104 receives a voice input with an explicit specification of a target device or device group, the voice-activated device 104 establishes a focus session with respect to the specified target device or device group. In some implementations, the voice-activated device 104 stores, for the focus session, a session start time (e.g., the timestamp of the voice input based on which the focus session was started) and, as the in-focus device for the focus session, the specified target device or device group. In some implementations, the voice-activated device 104 also logs subsequent voice inputs in the focus session. The voice-activated device 104 logs at least the most recent voice input in the focus session and optionally logs and retains preceding voice inputs within the focus session as well. In some implementations, the voice assistance server system 112 establishes the focus session. In some implementations, the focus session may be ended by a voice input explicitly specifying a different target device or device group.

While a focus session with respect to a device is active and the voice-activated device receives a voice input, the voice-activated device 104 makes one or more determinations with respect to the voice input. In some implementations, the determinations include: whether the voice inputs includes an explicit target device specification, whether the request in the voice input is one that can be fulfilled by the in-focus device, and a time of the voice input compared to the time of the last voice input in the focus session and/or the session start time. If the voice input does not include an explicit target device specification, includes a request that can be fulfilled by the in-focus device, and satisfies predefined time criteria with respect to the time of the last voice input in the focus session and/or the session start time, then the in-focus device is assigned as the target device for the voice input. Further details regarding focus sessions are described below.

Devices in the Operating Environment

FIG. 2 is a block diagram illustrating an example voice-activated device 104 that is applied as a voice interface to collect user voice commands in an operating environment (e.g., operating environment 100) in accordance with some implementations. The voice-activated device 104, typically, includes one or more processing units (CPUs) 202, one or more network interfaces 204, memory 206, and one or more communication buses 208 for interconnecting these components (sometimes called a chipset). The voice-activated device 104 includes one or more input devices 210 that facilitate user input, such as a button 212, a touch sense array 214, and one or more microphones 216. The voice-activated device 104 also includes one or more output devices 218, including one or more speakers 220, optionally an array of LEDs 222, and optionally a display 224. In some implementations, the array of LEDs 222 is an array of full color LEDs. In some implementations, a voice-activated device 104, depending on the type of device, has either the array of LEDs 222, or the display 224, or both. In some implementations, the voice-activated device 104 also includes a location detection device 226 (e.g., a GPS module) and one or more sensors 228 (e.g., accelerometer, gyroscope, light sensor, etc.).

Memory 206 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Memory 206, optionally, includes one or more storage devices remotely located from one or more processing units 202. Memory 206, or alternatively the non-volatile memory within memory 206, includes a non-transitory computer readable storage medium. In some implementations, memory 206, or the non-transitory computer readable storage medium of memory 206, stores the following programs, modules, and data structures, or a subset or superset thereof:

-   -   Operating system 232 including procedures for handling various         basic system services and for performing hardware dependent         tasks;     -   Network communication module 234 for connecting the         voice-activated device 104 to other devices (e.g., the voice         assistance service 140, one or more controllable devices 106,         one or more client devices 103, and other voice-activated         device(s) 104) via one or more network interfaces 204 (wired or         wireless) and one or more networks 110, such as the Internet,         other wide area networks, local area networks (e.g., local         network 108), metropolitan area networks, and so on;     -   Input/output control module 236 for receiving inputs via one or         more input devices and enabling presentation of information at         the voice-activated device 104 via one or more output devices         218, including:         -   Voice processing module 238 for processing audio inputs or             voice messages collected in an environment surrounding the             voice-activated device 104, or preparing the collected audio             inputs or voice messages for processing at a voice             assistance server system 112;         -   LED control module 240 for generating visual patterns on the             LEDs 222 according to device states of the voice-activated             device 104; and         -   Touch sense module 242 for sensing touch events on a top             surface (e.g., on touch sensor array 214) of the             voice-activated device 104;     -   Voice activated device data 244 for storing at least data         associated with the voice-activated device 104, including:         -   Voice device settings 246 for storing information associated             with the voice-activated device 104 itself, including common             device settings (e.g., service tier, device model, storage             capacity, processing capabilities, communication             capabilities, etc.), information of one or more user             accounts in a user domain, device nicknames and device             groups, settings regarding restrictions when dealing with a             non-registered user, and display specifications associated             with one or more visual patterns displayed by the LEDs 222;             and         -   Voice control data 248 for storing audio signals, voice             messages, response messages and other data related to voice             interface functions of the voice-activated device 104;     -   Response module 250 for performing instructions included in         voice request responses generated by the voice assistance server         system 112, and in some implementations, generating responses to         certain voice inputs; and     -   Focus session module 252 for establishing, managing, and ending         focus sessions with respect to devices.

In some implementations, the voice processing module 238 includes the following modules (not shown):

-   -   User identification module for identifying and disambiguating         users who provide voice inputs to the voice-activated device         104;     -   Hotword recognition module for determining whether voice inputs         include a hotword for waking up the voice-activated device 104         and recognizing such in the voice inputs; and     -   Request recognition module for determining a user request         included in a voice input.

In some implementations, memory 206 also stores focus session data 254 for an outstanding focus session, including the following:

-   -   Session in-focus device(s) 256 for storing an identifier of the         device or device group in focus in an outstanding focus session         (e.g., the device nickname, the device group name, MAC         address(es) of the device(s));     -   Session start time 258 for storing a timestamp for the start of         the outstanding focus session; and     -   Session command history 260 for storing a log of prior requests         or commands in the focus session, including at least the most         recent request/command. The log includes at least the         timestamp(s) of the logged prior request(s)/command(s).

Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, modules or data structures, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 206, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 206, optionally, stores additional modules and data structures not described above. In some implementations, a subset of the programs, modules, and/or data stored in the memory 206 can be stored on and/or executed by the voice assistance server system 112.

In some implementations, one or more of the modules in memory 206 described above are part of a voice processing library of modules. The voice processing library may be implemented and embedded on a wide variety of devices. An example of a voice processing library is described in U.S. Provisional Patent Application No. 62/334,434, entitled “Implementations for Voice Assistant on Devices,” filed May 10, 2016, which is incorporated by reference herein in its entirety.

FIGS. 3A-3B are block diagrams illustrating an example voice assistance server system 112 of a voice assistant service 140 of an operating environment (e.g., operating environment 100) in accordance with some implementations. The server system 112, typically, includes one or more processing units (CPUs) 302, one or more network interfaces 304, memory 306, and one or more communication buses 308 for interconnecting these components (sometimes called a chipset). The server system 112 may include one or more input devices 310 that facilitate user input, such as a keyboard, a mouse, a voice-command input unit or microphone, a touch screen display, a touch-sensitive input pad, a gesture capturing camera, or other input buttons or controls. Furthermore, the server system 112 may use a microphone and voice recognition or a camera and gesture recognition to supplement or replace the keyboard. In some implementations, the server system 112 includes one or more cameras, scanners, or photo sensor units for capturing images, for example, of graphic series codes printed on the electronic devices. The server system 112 may also include one or more output devices 312 that enable presentation of user interfaces and display content, including one or more speakers and/or one or more visual displays.

Memory 306 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Memory 306, optionally, includes one or more storage devices remotely located from one or more processing units 302. Memory 306, or alternatively the non-volatile memory within memory 306, includes a non-transitory computer readable storage medium. In some implementations, memory 306, or the non-transitory computer readable storage medium of memory 306, stores the following programs, modules, and data structures, or a subset or superset thereof:

-   -   Operating system 316 including procedures for handling various         basic system services and for performing hardware dependent         tasks;     -   Network communication module 318 for connecting the server         system 112 to other devices (e.g., client devices 103,         controllable devices 106, voice-activated devices 104) via one         or more network interfaces 304 (wired or wireless) and one or         more networks 110, such as the Internet, other wide area         networks, local area networks, metropolitan area networks, and         so on;     -   User interface module 320 for enabling presentation of         information (e.g., a graphical user interface for presenting         application(s) 322-328, widgets, websites and web pages thereof,         and/or games, audio and/or video content, text, etc.) at a         client device;     -   Command execution module 321 for execution on the server side         (e.g., games, social network applications, smart home         applications, and/or other web or non-web based applications for         controlling a client device 103, a controllable device 106, a         voice-activated device 104 and a smart home devices and         reviewing data captured by such devices), including one or more         of:         -   a cast device application 322 that is executed to provide             server-side functionalities for device provisioning, device             control, and user account management associated with cast             device(s);         -   one or more media player applications 324 that is executed             to provide server-side functionalities for media display and             user account management associated with corresponding media             sources;         -   one or more smart home device applications 326 that is             executed to provide server-side functionalities for device             provisioning, device control, data processing and data             review of corresponding smart home devices; and         -   a voice assistance application 328 that is executed to             arrange voice processing of a voice message received from             the voice-activated device 104 or directly process the voice             message to extract a user voice command and one or more             parameters for the user voice command (e.g., a designation             of a cast device or another voice-activated device 104); and     -   Server system data 330 storing at least data associated with         automatic control of media display (e.g., in an automatic media         output mode and a follow-up mode) and other data, including one         or more of:         -   Client device settings 332 for storing information             associated with one or more client device, including common             device settings (e.g., service tier, device model, storage             capacity, processing capabilities, communication             capabilities, etc.), and information for automatic media             display control;         -   Cast device settings 334 for storing information associated             with user accounts of the cast device application 322,             including one or more of account access information,             information for device settings (e.g., service tier, device             model, storage capacity, processing capabilities,             communication capabilities, etc.), and information for             automatic media display control;         -   Media player application settings 336 for storing             information associated with user accounts of one or more             media player applications 324, including one or more of             account access information, user preferences of media             content types, review history data, and information for             automatic media display control;         -   Smart home device settings 338 for storing information             associated with user accounts of the smart home applications             326, including one or more of account access information,             information for one or more smart home devices (e.g.,             service tier, device model, storage capacity, processing             capabilities, communication capabilities, etc.);         -   Voice assistance data 340 for storing information associated             with user accounts of the voice assistance application 328,             including one or more of account access information,             information for one or more voice-activated devices 104             (e.g., service tier, device model, storage capacity,             processing capabilities, communication capabilities, etc.);         -   User data 342 for storing information associated with users             in the user domain, including users' subscriptions (e.g.,             music streaming service subscriptions, video streaming             service subscriptions, newsletter subscriptions), user             devices (e.g., devices registered in the device registry 118             associated with respective users, device nicknames, device             groups), user accounts (e.g., users' email accounts,             calendar accounts, financial accounts), and other user data;         -   User voice profiles 344 for storing voice profiles of the             users in the user domain, including, for example, voice             models or voice fingerprints of the users and comfortable             volume level thresholds of the users; and         -   Focus sessions data 346 for storing focus sessions data for             multiple devices.     -   Device registration module 348 for managing the device registry         118;     -   Voice processing module 350 for processing audio inputs or voice         messages collected in an environment surrounding the electronic         device 104; and     -   Focus session module 352 for establishing, managing, and ending         focus sessions with respect to devices.

In some implementations, memory 306 also stores focus session data 346 for one or more outstanding focus sessions 3462-1 thru 3462-M, including the following:

-   -   Session source device 3464 for storing an identifier of the         device at which a focus session is established;     -   Session in-focus device(s) 3466 for storing an identifier of the         device or device group in focus in an outstanding focus session         (e.g., the device nickname, the device group name, MAC         address(es) of the device(s));     -   Session start time 3468 for storing a timestamp for the start of         the outstanding focus session; and     -   Session command history 3470 for storing a log of prior requests         or commands in the focus session, including at least the most         recent request/command.

In some implementations, the voice assistance server system 112 is primarily responsible for processing of voice inputs, and thus one or more of the programs, modules, and data structures in memory 206 described above with reference to FIG. 2 are included in respective modules in memory 306 (e.g., the programs, modules, and data structures included with voice processing module 238 are included in voice processing module 350). The voice-activated device 104 either transmits captured voice inputs to the voice assistance server system 112 for processing, or first pre-processes the voice inputs and transmits the pre-processed voice inputs to the voice assistance server system 112 for processing. In some implementations, the voice assistance server system 112 and the voice-activated device 104 has some shared and some divided responsibilities regarding processing of voice inputs, and the programs, modules, and data structures shown in FIG. 2 may be included in both or divided amongst the voice assistance server system 112 and the voice-activated device 104. Other programs, modules, and data structures shown in FIG. 2, or analogues thereof, may also be included in the voice assistance server system 112.

Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, modules or data structures, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 306, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 306, optionally, stores additional modules and data structures not described above.

Example Focus Session

FIGS. 4A-4D illustrate an example of a focus session in accordance with some implementations. In an operating environment with a voice-activated device 104 (e.g., operating environment 100) and multiple controllable devices 106, when a user in the environment makes a voice input specifying one of the controllable devices 106 as a target device, a focus session may be established with the target device as the in-focus device.

FIG. 4A shows a voice-activated device 404 (e.g., voice-activated device 104) and three controllable devices 406, 408, and 410 (e.g., controllable devices 106) in an operating environment (e.g., operating environment 100). The devices may be in the same space as a user 402 (e.g., in the same room) or spread throughout a structure in which the user is located. Device 406 is a speaker system nicknamed “master bedroom speaker.” Device 408 is a media device nicknamed “living room TV.” Device 410 is a media device nicknamed “game room TV.” There is no focus session at the moment; focus session 418 is empty.

The user 402 utters a voice input 403 “play cat videos on game room TV,” and the voice-activated device 404 receives the voice input. The voice-activated device 404 determines that the request in the voice input 403 is a request to play cat videos, and the target device is the “game room TV” device 410 explicitly specified in the voice input 403. A session 418 with the in-focus device being the “game room TV” device 410 is established at the voice-activated device 404, as shown in FIG. 4B. A command to play cat videos is sent (by the device 404 or the voice assistance server system 112) to the “game room TV” device 410, and the device 410 performs the operation 416.

Subsequently, while the session 418 with the “game room TV” 410 in focus is active and the operation 416 is being performed by the device 410, the user 402 utters another voice input “pause” 420. The voice-activated device 404 determines whether the voice input 420 includes a specification of a target device, and whether the request in the voice input 420 can be performed by the in-focus device 410. In the case of the specific voice input 420 “pause,” the voice-activated device 404 determines that the voice input 420 does not include a specification of a target device and that the request in the voice input (“pause” whatever is playing) can be performed by the in-focus device. In some implementations, determining whether the voice input 420 includes a specification of a target device includes looking for matches to device nicknames in the voice input (e.g., performing speech-to-text recognition on the voice input and parsing the text to look for device nicknames). In some implementations, determining whether request in the voice input can be performed by the in-focus device includes determining what the request in the voice input is and comparing the request to the command history (e.g., history 260) of the current focus session 418 for consistency with the last command in the session (e.g., a “pause music” request is inconsistent with a most recent command that is “pause music”), as well as comparing the request for consistency with capabilities of the in-focus device (e.g., a “pause music” request is inconsistent with the capabilities of a smart light).

In some implementations, the voice-activated device 404 also determines whether the voice input 420 meets one or more focus session maintenance criteria. In some implementations, a focus session maintenance criterion is that the timestamp of the voice input 420 is within a certain time from the timestamp of the last voice input 403 in the active session (e.g., the second voice input is received within a certain time of the preceding first voice input). In some implementations, there are multiple time thresholds for this criterion. For example, there may be a first, shorter time threshold (e.g., 20 minutes) and a second, longer time threshold (e.g., 4 hours). If the voice input 420 is received within the first, shorter threshold of the last voice input 403, and the other criteria above are satisfied, then the in-focus device is set as the target device for the voice input 420 (and, in some implementation, transmits this target device setting as well when transmitting the voice input 420 to the voice assistance server system 112 for processing). For example, voice input 420 is determined to not include a target device specification and that the request “pause” is consistent with the last command “play cat videos.” If the voice input 420 is received within the shorter time threshold of voice input 403, then the in-focus device, “game room TV” device 410, is set as the target device for voice input 420, and the operation 416 being performed at the “game room TV” device 410 is pausing the cat videos in accordance with the voice input 420, as shown in FIG. 4D.

If the voice input 420 is received after the first, shorter threshold, and within the second, longer threshold, of the last voice input 403, and the other criteria above are satisfied, the voice-activated device 404 outputs a voice prompt to request confirmation from the user that the in-focus device is the desired target device for the voice input 420. The voice-activated device 404, upon receiving confirmation that the in-focus device is the desired target device, maintains the session 418 and sets the in-focus device as the target device for the voice input 420 (and, in some implementation, transmits this target device setting as well when transmitting the voice input 420 to the voice assistance server system 112 for processing). If the user does not confirm the target device, the voice-activated device 404 may request that the user provide a target device specification, request that the user say the voice input again but include a target device specification, and/or end the session 418. In some implementations, if the voice input 420 is received after the second, longer threshold from of the last voice input 403, or the other criteria described above are not satisfied, the session 418 is ended. In some implementations, the values of these time thresholds are stored in memory 206 and/or memory 306. Time elapsed between voice inputs are compared to these thresholds.

In some implementations, the lack of an explicitly specified target device in the voice input and consistency of the request in the voice input with the last voice input and with the capabilities of the in-focus device are also considered to be focus session maintenance criteria.

Example Process

FIG. 5 is a flow diagram illustrating a method 500 of responding to a voice input of a user in accordance with some implementations. In some implementations, the method 500 is implemented at a first electronic device (e.g., voice-activated device 104) with one or more microphones, a speaker, one or more processors and memory storing one or more programs for execution by the one or more processors. This first electronic device is a member of a local group of connected electronic devices (e.g., voice-activated devices 104 and controllable devices 106 associated with a user account; controllable devices 106 associated with a particular voice-activated device 104) communicatively coupled (e.g., through networks 110) to a common network service (e.g., the voice assistance service 140).

The first electronic device receives (502) a first voice command including a request for a first operation. For example, a voice-activated device 404 receives a first voice input 403.

The first electronic device determines (504) a first target device for the first operation from among the local group of connected electronic devices. The voice-activated device 404 determines (e.g., based on processing by the voice processing module 238) a target device (or device group) for the voice input 403 from among the devices 406, 408, and 410. The voice-activated device 404 recognizes the target device specification “game room TV” in the voice input 403 as “game room TV” device 410.

The first electronic device establishes (506) a focus session with respect to the first target device (or device group). The voice-activated device 404 (e.g., the focus session module 252) establishes a focus session 418 with the “game room TV” device 410 as the in-focus device.

The first electronic device causes (508) the first operation to be performed by the first target device (or device group) via operation of the common network service. The voice-activated device 404 or the voice assistance server system 112 transmits a command, via the voice assistance service 140, to device 410 to perform the operation requested in voice input 403.

The first electronic device receives (510) a second voice command including a request for a second operation. The voice-activated device 404 receives a second voice input 420.

The first electronic device determines (512) that the second voice command does not include an explicit designation of a second target device (or device group). The voice-activated device 404 determines (e.g., based on processing by the voice processing module 238) a target device for the voice input 420, and recognizes that the voice input 420 does not include a target device specification.

The first electronic device determines (514) that the second operation can be performed by the first target device (or device group). The voice-activated device 404 determines that the operation requested in the voice input 420 is capable of being performed by the in-focus device 410 and is consistent with the last operation requested in voice input 403 and being performed by the in-focus device 410.

The first electronic device determines (516) whether the second voice command satisfies one or more focus session maintenance criteria. The voice-activated device 404 determines whether the voice input 420 is received within a certain time of the voice input 403.

In accordance with a determination that the second voice command satisfies the focus session maintenance criteria, the first electronic device causes (518) the second operation to be performed by the first target device (or device group) via operation of the common network service. The voice-activated device 404 determines that the voice input 420 is received within a first, shorter time threshold of voice input 403, and in accordance with that determination sets the target device for the voice input 420 to be the in-focus device 410. The voice-activated device 404 or the voice assistance server system 112 transmits a command, via the voice assistance service 140, to device 410 to perform the operation requested in voice input 420.

In some implementations, determining a first target device for the first operation from among the local group of connected electronic devices includes obtaining an explicit designation of the first target device from the first voice command. The voice-activated device 404 may pre-process the voice input 403 to determine if the voice input 403 includes an explicit specification of a target device. The voice-activated device 404 may, alternatively, receive the explicit specification of a target device from the voice assistance server system 112 that processed the voice input 403.

In some implementations, determining a first target device for the first operation from among the local group of connected electronic devices includes determining that the first voice command does not include an explicit designation of the first target device, determining that the first operation can be performed by a second electronic device among the local group of connected electronic devices, and selecting the second electronic device as the first target device. If the first voice input does not include an explicit specification of a target, but the request included within the first voice input is one that can be performed by a single device within the group (e.g., a video-related command and there is just one video-capable device in the group), then the single device is set as the target device for the first voice input. Further, in some implementations, if there is, besides the voice-activated device, just one controllable device, the controllable device is the default target device for voice inputs that do not explicitly specify a target device and whose requested operations can be performed by the controllable device.

In some implementations, a user's voice input history (e.g., collected by voice assistance server system 112 and stored in memory 306, collected by voice-activated device 104 and stored in memory 206) may be analyzed (e.g., by the voice assistance server system 112 or the voice-activated device 104) to determine if the history shows that a particular voice-activated device 104 is frequently used to control a specific controllable device 106. If the history does show such a relationship, the specific controllable device may be set as a default target device for voice inputs to the voice-activated device.

In some implementations, a specification (e.g., an identifier) of a default target device is stored at the voice-activated device 104 and/or the voice assistance server system 112.

In some implementations, in accordance with the determination that the second voice command satisfies the focus session maintenance criteria, extending the focus session with respect to the first target device. In some implementations, a focus session times out (i.e., ends) after a certain amount of time. The focus session 418 may be extended time-wise (e.g., reset the timeout timer) if the second voice input 420 satisfies the focus session maintenance criteria.

In some implementations, establishing the focus session with respect to the first target device includes storing a timestamp of the first voice command, and storing an identifier of the first target device. When a focus session is established after receiving the voice input 403, the voice-activated device 404 stores the time of the voice input 403 (e.g., in session command history 260) and an identifier of the in-focus device 410 (e.g., in session in-focus device 256).

In some implementations, the focus session maintenance criteria includes a criterion that the second voice command is received by the first electronic device within a first predefined time interval with respect to receiving the first voice command or with a second predefined time interval with respect to receiving the first voice command, the second predefined time interval succeeding the first predefined time interval; and determining whether the second voice command satisfies the one or more focus session maintenance criteria includes determining whether the second voice command is received within any of the first predefined time interval or the predefined second time interval. The voice-activated device 404 determines whether the voice input 420 satisfies one or more focus session maintenance criteria, including whether the voice input 420 is received within a first time threshold or a second time threshold of the voice input 403.

In some implementations, in accordance with a determination that the second voice command is received within the first predefined time interval, the first electronic device selects the first target device as a target device for the second voice command. If the voice input 420 is determined to be received within the first, shorter time threshold from the voice input 403, then the in-focus device 410 is set to be the target device for voice input 420.

In some implementations, in accordance with a determination that the second voice command is received within the second predefined time interval, the first electronic device outputs a request to confirm the first target device as a target device for the second voice command; and in accordance with a positive confirmation of the first target device in response to request to confirm, selects the first target device as a target device for the second voice command. If the voice input 420 is determined to be received outside the first, shorter time threshold, but within the second, longer time threshold, from the voice input 403, the voice-activated device prompts the user for confirmation of a target device (e.g., asks the user if the in-focus device 410 is the intended target device). If the user confirms that the in-focus device 410 is the intended target device, the in-focus device 410 is set as the target device for voice input 420.

In some implementations, the first electronic device receives a third voice command including a request for a third operation and an explicit designation of a third target device among the local group of connected electronic devices, ends the focus session with respect to the first target device, establishes a focus session with respect to the third target device, and causes the third operation to be performed by the third target device via operation of the common network service. The voice-activated device 404 may receive a new voice input, after voice input 420, that includes an explicit specification of a target device other than device 410 (e.g., device 406 or 408). In accordance with receipt of that voice input, the focus session 418 with device 410 in focus ends, and a new session with the new target device in focus is established. The voice-activated device 404 or the voice assistance server system 112 transmits a command, via the voice assistance service 140, to the new target device to perform the operation requested in the new voice input.

In some implementations, the first target device is the first electronic device. The first electronic device receives a fourth voice command including a request for a fourth operation and an explicit designation of a fourth target device among the local group of connected electronic devices, where the fourth target device is a third electronic device member of the local group of connected electronic devices, the third electronic device different from the first electronic device; maintains the focus session with respect to the first target device; and causes the fourth operation to be performed by the fourth target device via operation of the common network service. If the in-focus device for an active focus session 418 at the voice-activated device 404 is the voice-activated device 404 itself, and then a new voice input specifying a different device as the target is received after voice input 420, then the voice-activated device 404 or the voice assistance server system 112 transmits a command, via the voice assistance service 140, to the different target device to perform the operation requested in the new voice input, but the focus session is maintained with the voice-activated device 404 in focus.

In some implementations, the second voice command is received after the fourth operation is caused to be performed by the fourth target device, the first operation is a media playback operation, and the second operation is a media stoppage operation. The first electronic device receives a fifth voice command including a request for a fifth operation and an explicit designation of a fifth target device among the local group of connected electronic devices, where the fifth target device is the third electronic device; ends the focus session with respect to the first target device; establishes a focus session with respect to the fifth target device, and causes the fifth operation to be performed by the fifth target device via operation of the common network service. If the in-focus device for an active focus session 418 at the voice-activated device 404 is the voice-activated device 404 itself, and the voice input 403 included a request to initiate media playback, and the voice input 403 included a request to pause the media playing as a result of voice input 403, and a new voice input specifying a different device as the target is received after voice input 420, then the voice-activated device 404 or the voice assistance server system 112 transmits a command, via the voice assistance service 140, to the different target device to perform the operation requested in the new voice input, and the focus session with the voice-activated device in focus is ended, and a new focus session with the new target device in focus is established.

In some implementations, the first electronic device receives a fifth voice command including a predefined operation termination request, and in accordance with receiving the fifth voice command, causes the first operation to cease to be performed by the first target device, and ends the focus session with respect to the first target device. If the voice-activated device 404 receives a predefined termination command (e.g., “STOP”), the voice-activated device 404 or the voice assistance server system 112 transmits a command, via the voice assistance service 140, to device 410 to cease performing the operation 416, and the focus session 418 is ended.

In some implementations, the first operation is a media playback operation, and the second operation is one of: a media stoppage operation, a media rewind operation, a media fast forward operation, a volume up operation, and a volume down operation. The request in voice input 403 may be a request to initiate playback of media content (e.g., video, music), and the request in voice input 420 may be a request to control the playback (e.g., pause, rewind, fast forward, change volume up/down, next item/track, previous item/track, etc.)

In some implementations, the first operation is a device state change operation to a first state of a plurality of device states, and the second operation is a device state change operation to a second state of the plurality of device states. The request in voice input 403 may be a request to transition to a first state (e.g., turn light or device on, go to sleep mode), and the request in voice input 420 may be a request to transition to a second state (e.g., turn light or device off, wake from to sleep mode).

In some implementations, the first operation is a magnitude change operation in a first direction in a magnitude scale, and the second operation is a magnitude change operation in a second direction, opposite of the first direction, in the magnitude scale. The request in voice input 403 may be a request to change magnitude in one direction (e.g., brighten light, change volume up), and the request in voice input 420 may be a request to change magnitude in the opposite direction (e.g., dim light, change volume down).

In some implementations, the first electronic device includes an array of one or more LEDs. The first electronic device indicates a status of the focus session by illuminating one or more of the LEDs in the array of LEDs. The voice-activated device 404 may indicate that there is an active focus session, or other states and other information (e.g., indication of how long the focus session has been active or how much time has elapsed since the last voice input) associated with the focus session, by displaying patterns on the LED array.

In some implementations, focus sessions may be established per identified user. For example, if a user speaks a voice input specifying a target device, the user is identified and a focus session is established with respect to the identified user, with the target device specified in the voice input being in focus. If a different user speaks a voice input and specifies a different target device, the different user is identified and another focus session is established with respect to the identified different user, with the different target device being in focus. Voice inputs spoken by different users and not specifying a target device may be assigned different target devices based on the active focus session corresponding to the respective identified user. Examples of speaker identification are described in U.S. patent application Ser. No. 15/284,476, titled “Multi-User Personalization at a Voice Interface Device,” filed Oct. 3, 2016, which is incorporated by reference herein in its entirety.

Additional Examples of Focus Sessions

The following implementations describe implementations in a context of a voice-activated device 104 in a same room as one or more controllable devices 106 that are media devices. It should be appreciated that the implementations described below may be adapted to other types of controllable devices 106 (e.g., smart home devices) and to other device placement setups.

In some implementations, a focused session can be started with the in-focus device being a controllable device other than the voice-activated device if there is no media already playing on the voice-activated device. In some implementations, if media playing on the voice-activated device is paused, a focused session may be started with a controllable device other than the voice-activated device as the in-focus device.

In some implementations, a focused session is started if the user issues any valid request that has an explicit target device that is directed to a device or device group associated with the voice-activated device (and optionally on the same WiFi network as the voice-activated device). Examples of such valid requests include “play some music on my living room speakers,” “turn up the volume on the bedroom tv,” “next song on my Home Group,” and “pause the living room speakers.” The explicit target device becomes the in-focus device for the focus session.

In some implementations, if the request is clearly a request associated with video, and there is a single video-capable device amongst the associated controllable devices, then a focus session may be established with the video-capable device as the in-focus device.

In some implementations, if a request with another device as the target device is received while the voice-activated device is actively playing media, focus will remain on the voice-activated device, but once the voice-activated device stopped or paused its session, any new request to play or control media on another device moves the focus to that another device.

For example, the user requests “play Lady Gaga,” and the voice-activated device starts playing Lady Gaga music and starts a focus session with the voice-activated device in focus. The user then requests “pause,” and the voice-activated device pauses the Lady Gaga music (and maintains the focus session for, say, 2 hours). After 1 hour has passed, the user then requests “play cat videos on my TV.” The focus moves to the TV, and the TV starts playing cat videos.

As another example, the user requests “play Lady Gaga,” and the voice-activated device starts playing Lady Gaga music and starts a focus session with the voice-activated device in focus. The user then requests “show cat videos on my TV,” and the cat videos start showing on the TV, but focus remains on the voice-activated device. The user then requests “next,” the voice-activated device advances to the next track in the Lady Gaga music in accordance with the request. The user then requests “pause,” and music at the voice-activated device is paused. The user then requests “next slide on my TV,” and the next slide starts on the TV and focus is transferred to the TV.

In some implementations, a valid requests includes initiating music, initiating video, initiating news reading (e.g., reading out news articles), initiating podcasts, initiating photos (e.g., photo display or slideshow), and any media control command (other than a predefined STOP command that ends any current focus session.)

In some implementations, a focused session is ended when any of the following occurs:

-   -   focus session is transferred to a different device (via voice         input, e.g., the voice input explicitly specifying the different         device), and in this case a focused session is started with the         different device;     -   focus session starts or resumed (out of pause state) on the         voice-activated device via voice input or casting from another         device (e.g., via voice: “Play Lady Gaga on <nickname of         voice-interface device>”, “Play Lady Gaga locally”, etc.; via         casting: the user casts content to the voice-activated device         via an application on a client device);         -   however, if the voice-activated device is a member (follower             or leader) of the group that is about to play media, it will             not will not stop the focus (even though it is playing). So             focus will remain on the leader of the group (which might be             another voice-activated device);     -   when the request is a predefined “STOP” command (including all         relevant grammar) to the controllable device that is in-focus;     -   timeout related commands:         -   timeouts may be measured from the last request or command             given to the controllable device, whether the controllable             device is explicitly specified or set based on the in-focus             device of the focus session, other than the predefined             “STOP” command;         -   timeout may be 240 minutes across the various possible             commands; and     -   when the user press a button on the voice-activated device used         for pause/play (in addition this will also resume any paused         content locally on the voice-activated device).

In some implementations, the voice-activated device request user confirmation of the target device. The user is prompted for confirmation if he wants to play media on a controllable device as follows:

-   -   The prompt is triggered for media initiation (e.g., start music         where none had been playing) (vs media control, such as fast         forward or next track);     -   The prompt is triggered when a focus session is active; and     -   The prompt is triggered after some time (e.g., 20 minutes) has         passed from the last voice command from the current         voice-activated device given to the controllable device, whether         the controllable device is explicitly specified or set based on         the in-focus device of the focus session, other than the         predefined “STOP” command.

The prompt to confirm may be, for example:

-   -   The voice-activated device outputs “Would you like me to play on         <controllable device name>?”         -   User responds “Yes.” Then the requested media is played on             the in-focus controllable device and focus is maintained on             that device.         -   User responds “No.” Then the requested media is played on             the voice-activated device and the focus session is ended.         -   Other: if, for example, the user's response is unclear, the             voice-activated device may output “Sorry, couldn't             understand your response.”

In some implementations, when a focused session is initiated, media initiation and voice based control commands are applied to the in-focus controllable device. Non-media requests (e.g., searches, questions) are answered by the voice-activated device, and the non-media requests do not end the focus session.

In some implementations, even when a focused session has started, physical interactions will still control the voice-activated device, so physical interaction (e.g., pressing a button, touching a touch-sensitive area) with the voice-activated device to change volume and pause/play affects the voice-activated device and not necessarily the controllable device.

In some implementations, requests or commands issued to timers/alarms/text-to-speech playing on the voice-activated device has higher priority than similar requests or commands to the in-focus controllable device. For example, if the voice-activated device is ringing for a timer or an alarm, and the user utters “stop,” the voice-activated device stops the timer or alarm ringing. If the user then utters “volume <up/down>,” the timer or alarm ringing is still stopped, and the volume on the controllable device is changed up or down.

As another example, if the voice-activated device is playing text-to-speech (e.g., reading out the user's emails), and the user utters “stop,” the voice-activated device stops the text-to-speech reading. If the user then utters “volume <up/down>,” the volume on the voice-activated device is changed up or down.

As yet another example, if the voice-activated device is idle, paused, or app-loaded, and the user utters “stop,” media playing at the controllable device is stopped and the focus session is ended. If the user then utters “volume <up/down>,” the volume on the controllable device is changed up or down.

Proactive Voice Notifications

In some implementations, the operating environment 100 further includes an agent 116, as shown in FIG. 1. The agent 116 may be a system of one or more servers or other computing devices. The agent 116 implements an interface or a front-end to a service; users may access the service by interfacing with the agent 116. For example, the agent 116 may be an agent for a vacation reservation system (e.g., a service for reserving and booking flights, hotels, rental cars, etc.); users may interface with the agent 116 to check availability and pricing of flights, hotels, etc., and make reservations for the flights, hotels, etc. As another example, the agent 116 may be an agent for an online store or online delivery service; users may interface with the agent to view products or services for sale and make purchases. In some implementations, an agent 116 is a front end for a content host 114 that is the server system (e.g., the back end server system) for a service.

In some implementations, memory 206 (FIG. 2), or the non-transitory computer readable storage medium of memory 206, further stores the following programs, modules, and data structures, or a subset or superset thereof:

-   -   Conversation manager module 262 for managing and monitoring the         status of the user's interactions with the voice assistant         service 140 or agents 116, and determining whether the         interactions may be interrupted with notifications;     -   Notification manager module 264 for managing notifications to be         delivered to the user;     -   Agent module 266 for interfacing with an agent 116 of a service;     -   Notifications 268 for storing (e.g., queueing) notifications to         be provided to the user(s) associated with the device 104, and         optionally notifications configurations (e.g., what         notifications are provided, etc.) of the user(s) associated with         the device 104.

In some implementations, memory 306 (FIG. 3A), or the non-transitory computer readable storage medium of memory 306, further stores the following programs, modules, and data structures, or a subset or superset thereof:

-   -   Conversation manager module 354 for monitoring the status of the         user's interactions with the voice assistant service 140 or         agents 116, and determining whether the interactions may be         interrupted with notifications;     -   Notification manager module 356 for managing notifications to be         delivered to the user;     -   Agent module 358 for interfacing with an agent 116 of a service;         and     -   Per-user notifications 360 for storing (e.g., queueing)         notifications to be provided to users, and optionally         notifications configurations (e.g., what notifications are         provided, etc.) of the users.

In some implementations, one or more of the conversation manager module 262, notification manager module 264, and the agent module 266 can be implemented as part of one or more of the voice processing module 238 or the response module 250. In some implementations, one or more of the conversation manager module 262, notification manager module 264, and the agent module 266 can be implemented in whole or in part on the device 104 (FIG. 2) or on the voice assistance server system 112 (FIG. 3) (e.g., as conversation manager module 354, notification manager module 356, and the agent module 358, respectively).

Referring to FIG. 3C, in some implementations, a user 402 speaks to the device 104 and listens to output by the device 104 to interact with the voice assistant service 140 or with an agent 116 (e.g., through the agent module 266). For example, a user 402 makes one or more spoken requests that are processed and transmitted by the device 104 as one or more digital request messages 105. The requests 105 are performed and responded to by the voice assistant service 140 or the agent 116 (depending on the nature of the request) via one or more digital response messages 107. The digital response messages 107 are processed and played by the device 104 as output audible information for the user 402. A series of one or more request messages 105 and the related response messages 107 is sometimes referred to as a conversation, which can be brief (e.g., including a single request and response—as when a user asks about the current weather) or lengthy (e.g., including many requests 105 and responses 107 as part of a complex interaction between a user and an agent or voice assistant server—as when a user tries to book a restaurant or travel package).

Referring to FIG. 3D, in some implementations, the agent module 266 (and/or a voice assistant service 140 in some implementations) stores agent module information 267 indicative of the state of each request 105 that it is managing for a particular user 402 with respect to a particular agent 116, including one or more of:

-   -   User/device information 272 a related to the request (e.g., one         or more of user ID and account information, agent ID and         information, device ID and information, etc.);     -   a unique identifier 272 b for the associated request 105 (e.g.,         to allow requests 105 and responses 107 to be tracked and         associated with a conversation);     -   request initiation and completion times 272 c/272 d; and     -   a collection of indicators/flags 272 e related to the request,         including one or more of:         -   an indication 274 b that the agent 116 can support an             interruption in the conversation;         -   an indication 274 c that an interruption is in process;             and/or         -   an indication 274 d that a request 105 and the associated             user conversation has been completed.

In some implementations, the agent module 266 stores a library of transition-in and transition-out phrases 276 a/276 b from which it generates transitions-in and transitions-out 267 a/267 b for playback by the device 104 before and after playback of a proactive notification 263 (FIG. 3C). In some implementations, the agent module 266 is alerted by the conversation manager module 262 of availability of a notification 263 (e.g., by use of a notification request message 265 b). Thus, the agent module 266 is able to provide transitions before and after an interruption that are consistent (or intentionally not—depending on circumstances) with the language, style and vocal characteristics of the conversation being interrupted. Using transitions in this way makes delivery of a notification 263 less jarring and more effective than if it were inserted as an abrupt interruption in a conversation. In some implementations, the transitions 267 are tailored to the relative importance and/or urgency of a proactive notification 263 that they set off. For example, a proactive notification 263 that a meeting is about to begin or that a flight is boarding can be set off with a transition such as “Please note: <notification>” or “Please stay tuned for an important announcement: <notification>” (where “<notification>” represents playback of a notification 263) that is played at a louder than usual volume or with an urgent tone. On the other hand, a notification 263 of a sports score can use a more relaxed transition phrase and playback style.

Referring to FIG. 3C, the conversation manager module 262 tracks the state of interactions/conversations between the user 402 and the voice assistant service 140 or the agent 116. In some implementations, the conversation manager 262 receives this information from the agent module 266 (and/or voice assistant service 140) as conversation state information messages 141 that provide information such as whether the agent 116 can support an interruption in an active conversation. The conversation manager module 262 also monitors proactive notifications 263 generated by the notification manager module 264 for the user 402 (e.g., via notification requests 265 sent by the notification manager module 264). Proactive notifications 263 are responsive to pending user requests 109 or updates generated by components of the environment 100 and are distinct from requests 105. Based on conversation state information 141, the conversation manager module 262 determines whether and how to interrupt a conversation between the device 104 and the user 402 to deliver a proactive notification 263. In some implementations, the conversation manager module 262 delivers a notification 263 in a context sensitive manner that ensures that a notification 263 is more likely to be attended-to by the user 402 (e.g., due to being set off by transition phrases supplied by the agent module 266 that draw the user's attention to the proactive notification 263).

Referring to FIG. 3D, in some implementations, the conversation manager module 262 stores conversation manager module information 283 indicative of the state of one or more of the user's interactions with the voice assistant service 140 or agents 116 that it is monitoring. In some implementations the stored information 283 includes one or more of:

-   -   a unique identifier 282 b-i for each conversation being         monitored (e.g., to allow a conversation to be tracked and         associated with requests, responses and notifications);     -   conversation state information 141 a-i from the voice assistant         service 140;     -   conversation state information 141 b-i from the agent 116,         including one or more of:         -   an indication 274 b-i that the agent 116 can support an             interruption in the conversation;         -   an indication 274 d-i that a request 105 and the associated             user conversation have been completed; and     -   notification information 284-i provided by the notification         manager 264 (e.g., via a notification request message 265 a),         including a notification 263-i to be played on the device 104.

In some implementations, the conversation manager module 262 stores a library of transition-in and transition-out phrases 286 a/286 b that it can use to generate transitions 267 to be played by the device 104 before and/or after playback of a proactive notification 263. The transition phrases 286 a/286 b can be the same as or different from the transition phrases 276 a/276 b maintained by the agent module 266. In some implementations, the conversation manager module 262 generates transitions 267 when the agent 116 cannot support an interruption to a current conversation (as indicated in some implementations by the conversation interruptable indicator 274 b-i being set to “NO”). An advantage of using the conversation manager module 262 to generate transitions 267 is that this enables consistent transitions to be provided independent of a particular agent 266 that is being interrupted for playback of a notification 263, which helps to establish a recognizable voice and style for notifications 263 that enhances user recognition of those notifications.

Referring again to FIG. 3C, the conversation manager module 262 obtains information on proactive notifications or updates to be provided to the user (e.g., the notification manager module 264 sends information/notification requests 265 a to the conversation manager module 262, or the conversation manager module 262 periodically pings the notification manager module 264 for information on notifications), and thus the conversation manager module 262 also knows if there are proactive notifications or updates that need to be provided to the user. For example, if in the middle of a user/agent interaction a notification 263 is made in response to a pending request 109, the notification manager module 264 sends information on the notification 263 to the conversation manager module 262 (e.g., as a notification request 265 a, in response to which in some implementations the conversation manager module 262 checks with the agent module 266 via a second notification request 265 b whether the agent 116 can support an interruption for the notification 263).

Referring to FIG. 3D, in some implementations, the notification manager module 264 stores notification manager module information 293 indicative of the state of each pending request 109 and associated notification that it is managing for one or more users 402, including one or more of:

-   -   a unique identifier for a pending request 292 a that could         result in a proactive notification 263 or update;     -   pending request initiation and completion times 292 b and 292 c;     -   a future performance time 292 d for the pending request or an         indication 292 e that the future performance time is         indeterminate;     -   Notification information 298-i for one or more notifications,         including one or more of:         -   a proactive notification 263-i prepared for the user 402         -   Notification settings 297-i, such as a particular priority             level or type of the notification, indications that             processing/performing the pending request is complete and             that the proactive notification has been delivered to the             user (e.g., based on information provided by the             conversation manager module 262), and a number of times to             repeat the notification 263.

In some implementations, the notification manager module 264 stores a library of transition-in and transition-out phrases 296 a/296 b that it can use to generate transitions to be played by the device 104 before and/or after playback of a proactive notification 263. The transition phrases 296 a/296 b can be the same as or different from the transition phrases 276 a/276 b maintained by the agent module 266.

The conversation manager module 262 communicates with the agent 116 through the agent module 266 to ask the agent 116 if the agent 116 can support an interruption in its interaction with the user. If the agent 116 cannot, the conversation manager module 262 preempts the user's interaction with the agent 116 and immediately tells the user the notification (e.g., directs the device 104 to output the notification 263). The notification may voice out, for example, “sorry, but I need to interrupt, <notification>”.

If the agent 116 can support an interruption, the agent 116 will be given the opportunity to supply transition out and transition in outputs (e.g., voice outputs that indicate a transition into a notification and a transition back into the interaction).

For example, in the middle of an interaction with an agent 116 to make travel reservations, assume that a food delivery is close to arrival. The voice interaction between the user and the agent 116 may proceed like this:

-   -   Agent: I have your name and destination, but what kind of hotel         would you like?     -   User: I would like a . . .     -   Agent: I'll be right back.     -   Voice Assistant Service: Your Dominos pizza is about to arrive.     -   Agent: Thanks for waiting. Now, can you tell me again what kind         of hotel would you like?

In the example above, the output “I'll be right back” is a transition into a notification, and the output “Thanks for waiting. Now . . . ” is a transition back into the interaction. In some implementations, these outputs are supplied by the agent 116 or the agent module 266/358.

As another example, an interaction in which the notification arrives during a long text-to-speech output from the agent 116 may proceed as follows:

-   -   Agent: There are 15 hotels in this area for you to consider.         Hyatt Regency is a 4 star hotel located near . . .     -   Agent: Just a moment, I'll be right back to tell you about the         hotels in the area.     -   Voice Assistant Service: Your Dominos pizza is about to arrive.     -   Agent: OK, back to the hotels in the area, there is the Hyatt         Regency . . .

In the example above, the output “Just a moment, I'll be right back to tell you about the hotels in the area” is a transition into a notification, and the output “OK, back to the hotels in the area, there is . . . ” is a transition back into the interaction. In some implementations, these outputs are supplied by the agent 116 or the agent module 266/358.

In some implementations, proactive notifications can be enabled by a user request with a future performance time, such as the user ordering a pizza as in the example above, ordering a taxi to the airport, or requesting a notification when a particular event occur, such as a college football game starting, or a predicted rainstorm beginning. In some implementations, proactive notifications can also be enabled without any explicit user request and instead can be enabled based on programmed system behaviors that determine based on a number of conditions or information items being monitoring that the system needs to communicate an important notification to a user.

In this manner, important notifications can be delivered immediately, without completely stopping dialogs or interactions between the user and an agent, or having very abrupt/impolite transitions between agents the user is interacting with. Thus, notifications of important or imminent events are provided in a helpful, polite and useful manner via human/machine interactions—including providing by a voice assistant device in some instances important notifications via a natural and seamless interruption of another voice interaction. In some implementations, the generation and use by a voice assistant device/voice assistant server of transitional phrases between an active voice interaction and a proactive notification that is interrupting the interaction causes the interruption to feel as natural to a user as if the interaction and notifications were being handled by human assistant instead of computer-driven assistant supported by a combination of voice-responsive devices and remote voice interaction processing servers.

In some implementations, user personalization features and focus sessions as described herein are configured to interoperate with proactive notifications. For example, if a user for whom a current focus session is active is also a designated recipient of a proactive notification, then the electronic device that is participating in the active focus session with that user is also employed to provide the proactive notification that is designated for that user as described herein. In some implementations, if a proactive notification is particularly important, even if the designated recipient of the proactive notification is involved in a focus session with one of many voice assistant devices in a premise, the proactive notification can be played on the device that is participating in the focus session and other devices in the premise.

In some implementations, personalization features allow multiple proactive notifications to be managed in a voice assistant infrastructure by enabling the identification of one or more users who are participating in active voice assistant sessions in a premise (including focus sessions) and subsequent issuance of appropriate proactive notifications for each of the identified users via the respective devices being used by those individuals. Personalization features can also enable a voice assistant device to configure proactive notifications per individuals in a premise based on the identity of a user who is interacting with a particular voice assistant device.

FIG. 6 is a flow diagram illustrating a method 600 for proactive notifications in a voice interface device in accordance with some implementations. In some implementations, a method 600 for proactive notifications in a voice interface device includes receiving (602) a first user voice request for an action with an future performance time, assigning (604) the first user voice request to a voice assistant service for performance, subsequent to the receiving, receiving (606) a second user voice request and in response to the second user voice request initiating a conversation with the user; and during the conversation (608): receiving (610) a notification from the voice assistant service of performance of the action; triggering (612) a first audible announcement to the user to indicate a transition from the conversation and interrupting the conversation; triggering (614) a second audible announcement to the user to indicate performance of the action; and triggering (616) a third audible announcement to the user to indicate a transition back to the conversation and rejoining the conversation. In some implementations, the method is implemented at a voice-activated electronic device (e.g., device 104) or at a server system of a voice assistant service 140 (e.g., voice assistance server 112).

In some implementations, one or more of the audible announcements are accompanied by a visual cue displayed on a user voice interface device. In some implementations, the visual cues can be provided via display elements of the device in accordance with elements of the LED design language described herein.

In some implementations, the first user voice request is received at a user voice interface device, which can be a voice assistance device with one or more speakers and one or more microphones (e.g., a GOOGLE HOME device or similar), a mobile phone, a tablet, or a laptop.

In some implementations, the future performance time is indeterminate. For example, the future performance time might not be part of the user request, hard to determine, or can occur in a range of times (as with the pizza delivery request). In addition, if there is no explicit user request that gives rise to a proactive notification (e.g., when a voice assistant device is configured to provide a proactive notification upon occurrence of one of a number of monitored conditions), the future performance time could be any time. In some implementations, in these or other similar situations, the proactive notification (whenever it needs to be issued) and any resulting interruption of ongoing user interactions with a voice assistant device are managed as described herein.

In some implementations, the voice assistant service is implemented at a server in communication with the user voice interface device.

In some implementations, the conversation is monitored by a digital conversation manager implemented at a server in communication with the user voice interface device.

In some implementations, the digital conversation manager receives the notification.

In some implementations, the method further includes determining based on context of the conversation an appropriate time at which to trigger the first audible announcement.

In some implementations, the conversation is performed between the user and a software agent, where the software agent determines and generates one or more of the audible announcements.

Reference has been made in detail to implementations, examples of which are illustrated in the accompanying drawings. In the detailed description above, numerous specific details have been set forth in order to provide a thorough understanding of the various described implementations. However, it will be apparent to one of ordinary skill in the art that the various described implementations may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the implementations.

It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first device could be termed a second device, and, similarly, a second device could be termed a first device, without departing from the scope of the various described implementations. The first device and the second device are both types of devices, but they are not the same device.

The terminology used in the description of the various described implementations herein is for the purpose of describing particular implementations only and is not intended to be limiting. As used in the description of the various described implementations and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting” or “in accordance with a determination that,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event]” or “in accordance with a determination that [a stated condition or event] is detected,” depending on the context.

For situations in which the systems discussed above collect information about users, the users may be provided with an opportunity to opt in/out of programs or features that may collect personal information (e.g., information about a user's preferences or usage of a smart device). In addition, in some implementations, certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user's identity may be anonymized so that the personally identifiable information cannot be determined for or associated with the user, and so that user preferences or user interactions are generalized (for example, generalized based on user demographics) rather than associated with a particular user.

Although some of various drawings illustrate a number of logical stages in a particular order, stages that are not order dependent may be reordered and other stages may be combined or broken out. While some reordering or other groupings are specifically mentioned, others will be obvious to those of ordinary skill in the art, so the ordering and groupings presented herein are not an exhaustive list of alternatives. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.

The foregoing description, for purpose of explanation, has been described with reference to specific implementations. However, the illustrative discussions above are not intended to be exhaustive or to limit the scope of the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The implementations were chosen in order to best explain the principles underlying the claims and their practical applications, to thereby enable others skilled in the art to best use the implementations with various modifications as are suited to the particular uses contemplated. 

What is claimed is:
 1. A method implemented at an electronic voice interface device including a speaker, one or more processors, and memory storing instructions for execution by the one or more processors, the method comprising: receiving a first voice request; assigning the first voice request to a server-implemented voice assistant service; subsequent to the receiving of the first voice request: receiving a second voice request; and assigning the second voice request to the server-implemented voice assistant service as part of a user interaction; and subsequent to the receiving of the second voice request: receiving from the server-implemented voice assistant service a response to the first voice request; receiving from the server-implemented voice assistant service a response to the second voice request as part of the user interaction; triggering an audible announcement indicating a transition from the user interaction; and following the audible announcement and prior to triggering any announcements related to the user interaction including the response to the second voice request, triggering a verbal announcement including the response to the first voice request.
 2. The method of claim 1, further comprising: following the triggering of the verbal announcement including the response to the first voice request, triggering an audible announcement indicating a transition back to the user interaction; and following the triggering of the audible announcement indicating a transition back to the user interaction, triggering a verbal announcement related to the user interaction including the response to the second voice request.
 3. The method of claim 1, wherein: the first voice request is a request for an action with a future performance time; the response to the first voice request includes a notification indicating performance of the action; the second voice request is a request for information; the response to the second voice request includes the requested information; and the electronic voice interface device receives the second voice request prior to the future performance time.
 4. The method of claim 1, further comprising determining based on context of the user interaction an appropriate time at which to trigger the audible announcement indicating a transition from the user interaction.
 5. The method of claim 1, wherein: the user interaction is performed between a user of the electronic voice interface device and a software agent; and the software agent determines and generates the audible announcement indicating a transition from the user interaction.
 6. The method of claim 5, wherein: the software agent performs operations related to satisfaction of the second voice request; and an agent module manages interactions between the software agent and the user during the user interaction.
 7. The method of claim 6, wherein: the agent module comprises a library of transition-in phrases and a library of transition-out phrases; the agent module generates content of the audible announcement indicating a transition from the user interaction from one or more of the transition-in phrases; and the agent module generates content of the audible announcement indicating a transition back to the user interaction from one or more of the transition-out phrases.
 8. The method of claim 7, wherein a conversation manager module causes the agent module to: interrupt the user interaction; trigger the audible announcement indicating a transition from the user interaction; wait for the conversation manager module to trigger the verbal announcement including the response to the first voice request; trigger the audible announcement indicating a transition back to the user interaction upon completion of the verbal announcement including the response to the first voice request; and rejoin the user interaction.
 9. An electronic voice interface device comprising a speaker, one or more processors, and memory storing executable instructions that are configured to cause the one or more processors to perform operations including: receiving a first voice request; assigning the first voice request to a server-implemented voice assistant service; subsequent to the receiving of the first voice request: receiving a second voice request; and assigning the second voice request to the server-implemented voice assistant service as part of a user interaction; and subsequent to the receiving of the second voice request: receiving from the server-implemented voice assistant service a response to the first voice request; receiving from the server-implemented voice assistant service a response to the second voice request as part of the user interaction; triggering an audible announcement indicating a transition from the user interaction; and following the audible announcement and prior to triggering any announcements related to the user interaction including the response to the second voice request, triggering a verbal announcement including the response to the first voice request.
 10. The electronic voice interface device of claim 9, wherein the instructions are further configured to cause the one or more processors to perform: following the triggering of the verbal announcement including the response to the first voice request, triggering an audible announcement indicating a transition back to the user interaction; and following the triggering of the audible announcement indicating a transition back to the user interaction, triggering a verbal announcement related to the user interaction including the response to the second voice request.
 11. The electronic voice interface device of claim 9, wherein: the first voice request is a request for an action with a future performance time; the response to the first voice request includes a notification indicating performance of the action; the second voice request is a request for information; the response to the second voice request includes the requested information; and the electronic voice interface device receives the second voice request prior to the future performance time.
 12. The electronic voice interface device of claim 9, wherein the instructions are further configured to cause the one or more processors to determine based on context of the user interaction an appropriate time at which to trigger the audible announcement indicating a transition from the user interaction.
 13. The electronic voice interface device of claim 9, wherein: the user interaction is performed between a user of the electronic voice interface device and a software agent; and the software agent determines and generates the audible announcement indicating a transition from the user interaction.
 14. The electronic voice interface device of claim 13, wherein: the software agent performs operations related to satisfaction of the second voice request; and an agent module manages interactions between the software agent and the user during the user interaction. the agent module comprises a library of transition-in phrases and a library of transition-out phrases; the agent module generates content of the audible announcement indicating a transition from the user interaction from one or more of the transition-in phrases; and the agent module generates content of the audible announcement indicating a transition back to the user interaction from one or more of the transition-out phrases.
 15. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which, when executed by an electronic voice interface device with one or more processors, cause the one or more processors to perform: receiving a first voice request; assigning the first voice request to a server-implemented voice assistant service; subsequent to the receiving of the first voice request: receiving a second voice request; and assigning the second voice request to the server-implemented voice assistant service as part of a user interaction; and subsequent to the receiving of the second voice request: receiving from the server-implemented voice assistant service a response to the first voice request; receiving from the server-implemented voice assistant service a response to the second voice request as part of the user interaction; triggering an audible announcement indicating a transition from the user interaction; and following the audible announcement and prior to triggering any announcements related to the user interaction including the response to the second voice request, triggering a verbal announcement including the response to the first voice request.
 16. The non-transitory computer readable storage medium of claim 15, wherein the instructions are further configured to cause the one or more processors to perform: following the triggering of the verbal announcement including the response to the first voice request, triggering an audible announcement indicating a transition back to the user interaction; and following the triggering of the audible announcement indicating a transition back to the user interaction, triggering a verbal announcement related to the user interaction including the response to the second voice request.
 17. The non-transitory computer readable storage medium of claim 15, wherein: the first voice request is a request for an action with a future performance time; the response to the first voice request includes a notification indicating performance of the action; the second voice request is a request for information; the response to the second voice request includes the requested information; and the electronic voice interface device receives the second voice request prior to the future performance time.
 18. The non-transitory computer readable storage medium of claim 15, wherein the instructions are further configured to cause the one or more processors to determine based on context of the user interaction an appropriate time at which to trigger the audible announcement indicating a transition from the user interaction.
 19. The non-transitory computer readable storage medium of claim 15, wherein: the user interaction is performed between a user of the electronic voice interface device and a software agent; and the software agent determines and generates the audible announcement indicating a transition from the user interaction.
 20. The non-transitory computer readable storage medium of claim 19, wherein: the software agent performs operations related to satisfaction of the second voice request; and an agent module manages interactions between the software agent and the user during the user interaction. the agent module comprises a library of transition-in phrases and a library of transition-out phrases; the agent module generates content of the audible announcement indicating a transition from the user interaction from one or more of the transition-in phrases; and the agent module generates content of the audible announcement indicating a transition back to the user interaction from one or more of the transition-out phrases. 